Netware Super Library

home *** CD-ROM | disk | FTP | other *** search

/ Netware Super Library / Netware Super Library.iso / acss_com / stpe301 / stompere.doc < prev next >

Wrap

Text File | 1995-07-05 | 41.8 KB | 1,258 lines

Stomper 3.0 Modemsharing-Software for Novell or Netbios based networks DOS/Windows (C) 1994,1995 Pflug Datentechnik. Hardware and software requirements for installation: - network, preferably Personal NetWare, Novell NetWare lite, NetWare >=3.11 or Netbios network (Lantastic) - minimum DOS 3.3 - Windows 3.1 if available - 1 serial interface per modem server, if possible FIFO buffered (UART 16550) - Processor depending on number of modem servers on one computer, minimum AT (80286) 1 The Concept 1.1 What is a modem-/ISDN-server? 1.2 Server-Client Operation 2 Installation 2.1 fast installation 2.2 Complete Installation 2.2.1 The Queuemanager 2.2.2 The modem server 2.2.3 The Client 2.2.4 Windows-Modemsharing 2.2.5 The ISDN server 2.2.6 The ISDN-client 3 Select Specific Modemservers By Different Ports 4 the Cooperative Mode 5 Queue Management 6 The Monitor 7 Programs Using INT 14 (BIOS) 8 Stomper And Windows For Workgroups / Windows 95 8.1 Microsoft Network 8.2 Novell Network 9 Installation On A Netware Fileserver (NLM-Version) 10 Applying Access Rights Appendix A Suitable Programs Appendix B NETINFO.EXE Appendix C Tips 1. Telemate 2. Terminate 3. Telix For Windows 4. pcAnywhere Appendix D Troubleshooting Appendix E What is a FOSSIL driver? Appendix F What is a network fossil driver? Appendix G How to order Appendix H Support 1 The Concept ~~~~~~~~~~~~~~~ 1.1 What is a modem-/ISDN-server? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The modemserver is a small program, that accesses the device directly, that should be made available throughout the network. There may be more than one modemserver (or ISDN-server) on one computer oder there may be several servers spread over the whole network. When a client accesses a modemserver, all communication between communication software (terminal, fax, ...) and the modem is directed through the network. Stomper is responsible for repacking the data suitable for the network, to send it and to convert it back. It appears to the user as if the modem was attached directly to his local workstation. Often the modemserver is compared to a printerserver. This is not quite correct. The main difference is, that the printer server is "batch-driven". This means, that a print job is placed into a temporary file, which is read by the printer server whenever it is ready and the contents then are sent to the printer. A modemserver works online. All data is sent to the device immediately. Additionally all line-control information is passed on. 1.2 Server-Client Operation ~~~~~~~~~~~~~~~~~~~~~~~~~~~ As soon as a client requests an available modem or an ISDN-adapter (this happens automatically, when your communications software is started), the client-program (NETFOS, NFCAPI, ...) searches for a modemserver and initiates a session. From this moment on, the server is not available for other stations. It is reserved for this one client. At the end of the session, the server will get released. 2 Installation ~~~~~~~~~~~~~~~~ 2.1 fast installation ~~~~~~~~~~~~~~~~~~~~~ First of all, the queue manager STMGR is loaded on any available workstation in the network. This could be a computer not integrated in the modem sharing, or a modem server. If you intend to run Stomper in a Novell Netware 3.11 or higher network, we strongly recommend to install STMGR.NLM on the fileserver rather than installing the queuemanager on a DOS station. Refer to chapter Installation on a NetWare fileserver (NLM-version) on page 28. Please read chapter 4, waiting queue administration, in this context. 1. Modemsharing ~~~~~~~~~~~~~~~~ To install a modemserver, load STOMPER /Px (x = number of the port ; 1 = COM1) To install a modem client, load: NETFOS /Px (x = number of the port) NETFOS now serves all applications, that use a FOSSIL driver. For BIOS-INT14 or Windows-COMM.DRV, read the next chapter. 2. ISDN-Sharing ~~~~~~~~~~~~~~~ To install an ISDN-server, load: STISDN To install an ISDN-client, load: NFCAPI Now your ISDN-applications can access NFCAPI(CAPI v1.1) 2.2 Complete Installation ~~~~~~~~~~~~~~~~~~~~~~~~~ Stomper either works with the IPX- or the Netbios protocol. In Novell networks IPX is loaded already, so nothing else has to be done. Others (for example Lantastic: AILANBIO), however, require the installation of the Netbios driver. Most network types (NetWare/NetWare Lite, Lantastic...) supply Netbios. With the use of Netbios Stomper becomes independent of the available network. 2.2.1 The Queuemanager ~~~~~~~~~~~~~~~~~~~~~~~~~ The Queuemanager performs the following tasks: 1. "Tracker", observes the status of all modem servers installed in the network, containing the following information: Status of the modem server (busy/free), the Client (Netfos) which is presently served, number of bytes transmitted in a session. This information is analysed and displayed for example by STMON, the monitor program. 2. "Queue manager", allocates free modem servers to the clients. In order to avoid chaos, the queue manager can only exist once in the network. When STMGR is loaded for a second time in the network, only the tracker part will be loaded automatically. 3. IPX routing. The transmitter must always know the destination network in order to transport IPX packets over several network segments. STMGR therefore gives his address to all routers in the network (the file server can also work as a router and therefore adds this address to its bindary). Stomper identifies this address by ordering it form the nearest router. When the queue manager allocates a modem server to a client, the network address of stomper is supplied to the client. 4. Logging. If the option /L is specified, a log file will be generated, that logs all actions. 5. Stationrestrictions (only STMGR.NLM) See Chapter Applying access rights. Command line parameters If you intend to run Stomper in a Novell Netware 3.11 or higher network, we strongly recommend to install STMGR.NLM on the fileserver rather than installing the queuemanager on a DOS station. Refer to chapter Installation on a NetWare fileserver (NLM-version) on page 28. STMGR [/F] [/U] [/L.....] [/A] /U is given to remove an installed STMGR from the memory /F the queue manager uses netbios, even if IPX is loaded /L generates a logfile. examples: STMGR /LSTOMPER.LOG generates STOMPER.LOG in the directory, in which STMGR.COM resides. STMGR /LC:\TEMP\ST.LOG generates C:\TEMP\ST.LOG /A Allow "autoattach". See also: NETFOS /A please note, that if you wish to create a logfile in a desired directory, you must specify a complete path! 2.2.2 The modem server ~~~~~~~~~~~~~~~~~~~~~~~~~ The modemserver accesses the modem (or another device connected to the RS-232-port). Apart from the application data, the line-condition will be updated whenever necessary. This condition includes DCD (Data Carrier Detect), DTR (Data Terminal Ready), RI (Ring Indicator), DSR (Data Set Ready), RTS (Ready To Send) and CTS (Clear To Send). For DOS there are 2 variants of the modemserver: · STOMPER.COM accesses the serial port directly · STOMPERF.COM uses a FOSSIL driver to communicate with the hardware Using the latter, makes it possible to share any communications-hardware in the network, as long as there is an apropriate FOSSIL driver available (like CFOS for ISDN). For information on how to install a modemserver on a NetWare fileserver, refer to chapter Installation on a NetWare fileserver (NLM-version) Command line parameters STOMPER [/Px] [/Na] [/Lxxxxxx] [/U] [/F] [/Qxx] [/Bxxxx] [/Caaa...] [/R] The parameters are optional: /P selects the COM port for the modem, for example /P2 for COM2. If omitted, COM1 is selected automatically. /U is given to remove any already installed STOMPER from the memory. This is only possible while Stomper is not active. /F STOMPER is told to use Netbios exclusively (even if IPX is loaded) /Q for unconventional IRQs. /Q7 => IRQ7 /B for unconventional ports. /B3E8 => Port 3E8 /C Cooperative mode: see chapter 3, Cooperative mode /L Lock Baud. Independent of the bps rate chosen by the application (terminal program,...), Stomper always selects automatically the bps rate of this parameter, for example /L57600 (locked). Attention: Windows applications ignore this parameter! /N one single character is added to this option (for example one letter or one digit), giving the modem server an individual identification. Each modem server has to be identified individually (several modem servers on one computer have individual characters). /R ensures RTS/CTS data flow control. This is very helpful, for example if you encounter problems when sending with Winfax. Normally this option does not influence any other applications. /Z 16550 FIFO buffer control /Z0 FIFO off /Z1 FIFO on 1 byte threshold /Z4 FIFO on 4 byte threshold /Z8 FIFO on 8 byte threshold (default) /Z14FIFO on 14 byte threshold It is not recommended to use this parameter! Stomper normally selects an 8 byte threshold for the FIFO buffer, which causes the least potential errors. On very slow PCs (286 - 6 MHz), it may be necessary to use /Z1. 2.2.3 The Client ~~~~~~~~~~~~~~~~~~~ The modem client provides access to a modemserver. All applications that can use a FOSSIL driver or BIOS-INT14 (option /I) can use it to access a network modem. Command line parameters NETFOS [/Px] [/U] [/I] [/F] [/Naaa...] [/A|/A+] /P specifies which COM port will be redirected, for example. /P2 for COM2. COM1 is chosen automatically when this parameter is not used. /U is given to remove an installed NETFOS from the memory. /I This parameter is necessary to redirect programs which communicate using the BIOS-INT-14. With this parameter given, Netfos finds out if an application is able to serve a fossil interface, and reacts accordingly. Without this parameter Netfos can only serve Windows programs or programs which support a fossil driver. /F Netfos uses Netbios (even if IPX is loaded) /N All modem servers wanted in the network are listed here. When for example. /N123 is given, the queuemanager selects the first available modem server from the list. The priority is from left to right, so that the queuemanager selects STOMPER /N2 when STOMPER /N1 is occupied. This option is invalid (and meaningless) In the 1-server version. /A "Autoattach"-mode. When a modemserver is assigned to a user after he was placed in the queue (waiting for a modemserver to become available), this option suppresses the message "Connected to modemserver". So the connection will be established without interaction. For both /A and /A+ STMGR must have been loaded with the option /A as well! /A+ Same as /A, but additionally the user will be placed into the waitingqueue automatically, in case there is no modemserver available. This mode runs completely unattended. Note that the parameter /Px does not have to be identical for the two drivers. For Stomper /Px defines the interface which is physically connected with the modem. For Netfos /Px defines only the interface which is addressed by the terminal program. 2.2.4 Windows-Modemsharing ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In the file SYSTEM.INI (Windows directory) change the following line in the [boot]-section: comm.drv=comm.drv change into comm.drv=stcomm.drv Make sure that there is only one line of comm.drv=...!! Attention! After Winfax installations comm.drv is usually changed into wfxcomm.drv. This can be replaced without problems. STCOMM.DRV should be placed on a DOS path or in a windows directory. Alternatively, the whole path can be given. 2.2.5 The ISDN server ~~~~~~~~~~~~~~~~~~~~~ The ISDN server (STISDN) makes a CAPI accessible by the clients (NFCAPI). An STISDN can only serve one client at a time. To let more than one client access the CAPI at the same time, STISDN has to be loaded multiple times. These can use the same CAPI, depending on how many applications this CAPI can support (usually 2 to 4). Command line parameters STISDN [/Na] [/U] [/F] [/M...] /U is given to remove any already installed STISDN from the memory. This is only possible while STISDN is not active. /F STISDN is told to use Netbios exclusively (even if IPX is loaded) /N one single character is added to this option (for example one letter or one digit), giving the modem server an individual identification. Each ISDN server has to be identified individually (several ISDN servers on one computer have individual characters). /M... defines, how much memory is reserved for communications. The default is 16384 Bytes. Values from 4000-65500 Bytes are accepted. The optimum depends on the software you will be using and the number of concurrent ISDN-connections. The default value usually is enough for 1 application with channel-bundeling or two concurrent applications using each a single ISDN-connection. 2.2.6 The ISDN-client ~~~~~~~~~~~~~~~~~~~~~~ The ISDN cclient (NFCAPI) provides applications with a virtual CAPI v1.1- interface. Up to 4 applications can be serviced by the same NFCAPI. Command line parameters NFCAPI [/U] [/F] [/Naaa...] [/A|/A+] /U is given to remove an installed NFCAPI from the memory. /F NFCAPI uses Netbios (even if IPX is loaded) /N All ISDN servers wanted in the network are listed here. When for example, /N123 is given, the queuemanager selects the first available ISDN server from the list. The priority is from left to right, so that the queuemanager selects STISDN /N2 when STISDN /N1 is occupied. This option is invalid (and meaningless) In the 1-server version. /A "Autoattach"-mode. When a ISDN server is assigned to a user after he was placed in the queue (waiting for a ISDN server to become available), this option suppresses the message "Connected to ISDN server". So the connection will be established without interaction. For both /A and /A+ STMGR must have been loaded with the option /A as well! /A+ Same as /A, but additionally the user will be placed into the waitingqueue automatically, in case there is no ISDN server available. This mode runs completely unattended. 3 Select specific modemservers by different ports ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Example: You have 5 modem-/ISDN-servers installed in your network: · three modems with IDs 1, 2 and 3 · two ISDN-lines with IDs 4 and 5 Of course you will want to use an ISDN-line, when you need an ISDN-line and a modem line, when you need a modem line. You can do this by simply entering the following command line: NETFOS /P1(123) /P2(45) When your Application addresses COM1, you will get connected to modemserver 1, 2 or 3, whichever is available. When your application uses COM2, one of th ISDN lines will be selected. Note that there is no option /N specified, since this is completely replaced by the values in brackets. You can specify up to 4 ports. Of course you can use this method to distinguish different modemtypes as well - ISDN was chosen as a typical example of different transport media. 4 The Cooperative Mode ~~~~~~~~~~~~~~~~~~~~~~~~ This mode - under certain circumstances - enables the use of another software (for example a mailbox) on the modem server - sharing the port cooperatively with Stomper. Parameter: /Cxxxxx xxxxx stands for any modem command. At the end of a session this command is sent to the modem in order to re-initialize it. CR/LF is added to this string (for example. ATZ), automatically. Thus the modem server can run a mailbox, which will be stopped automatically when a client in the network demands the modem. While a caller is logged into the mailbox, Stomper is inactive. In order to avoid fatal failures on the computer, please read the following lines even if this sounds a bit technical: For safety reasons a network-modem demand is rejected, when the CD signal is active, for example, when someone is logged into the mailbox. Stomper will also be blocked for another 60 seconds after the last ring. This mode has to be handled with care, as it is quite rude to block an application just like that, but this can be done for example with FrontDoor and Remote Access. As during the blocking of the modem the bps-rate could be changed, at the end of such a session Stomper sends an optional command (see above, "/Caaa") to the modem in order to set the correct bps rate. For this, the modem must have an automatic baudrate identification. In the cooperative mode Stomper MUST NOT BE LOADED in the high memory area(UMB), due to the following: The computer will be stopped at an appropriate time, that is in the moment of a timer interrupt (produced by the computer 18 times per second). "Appropriate" means: 1. there is no hard disk or disk access 2. Windows is inactive 3. The program interrupted is placed in the memory above stomper and under the high memory area from A000:0000 on. No. 3 ensures that no IPX routine has been interrupted. As Stomper depends on IPX, it would not dare to touch this without being affected personally. As Stomper needs the IPX (or Netbios) drivers, they are normally placed in a lower memory section or in an UMB. But if Stomper has also been loaded in the high memory area, there is no certainty where the network drivers are placed related to Stomper. It is possible that the interrupt does not appear. This happens for example. when the command line in DOS is used, which is mainly executed in COMMAND.COM (below Stomper) or in BIOS (>A000). The use of the interface is not affected in this case. 5 Queue Management ~~~~~~~~~~~~~~~~~~~~ In order to enable a precise access to one or several modem servers in the network, the program STMGR.COM has to be loaded on one computer (any) in the network. STMGR.COM should already be active in the network, before a Client (Netfos) or modem server (Stomper) is loaded. Preferably this program should be installed on a modem server. If you are working with Novell Netware, the best choice will be the Fileserver (STMGR.NLM) This program operates completely in the background and does not require much memory. The queue manager's strategies When a client demands a modem server, the queue manager tries to allocate a free modem server which is selected by NETFOS /Naaa...(from left to right). In case all modem servers are busy, the client computer receives the following message: No modemserver available. Queue in? Y/N After confirming Y, the following message appears: Queued in. Wait in foreground? Y/N Now there are two possibilities: 1. "Wait in the background" (N) tells the application that no fossil driver is installed (not recommended for pure BIOS INT14 applications). The computer can be used and as soon as a modem server is free, the following message appears: Connected to modem server (ENTER) The queue manager marks the modem server as "reserved". The user has 1,5 minutes to start his application and to use the modem server. 2. While waiting in the foreground, the following message appears Waiting for modem server... (ESC) In the meantime the computer cannot be used for other applications. Under windows this process is executed accordingly, but only the application in use is paused. 6 The Monitor ~~~~~~~~~~~~~~~ The monitor (STMON.EXE) provides an overview over the modem servers installed in the network and the proceedings can be observed. The monitor is started by loading STMON As STMON displays the information obtained from the tracker, it depends on STMGR.COM being loaded. If STMGR is not already in memory, the monitor will load it automatically. For this, however, STMGR.COM must be either - in the same directory as STMON.EXE or - in the DOS path. Attention: The monitor must not be started in a DOS box under windows! The monitor displays ten sections on the screen, each containing information of an individual modem server. Field identifications: - Network address - individual address in the network which is preset by the network adaptor. In order to obtain a better overview, a file called NODES.LST can be created, in which names are allocated to the network addresses. An example for such a file: 924e32a John's abacus 80ca23e5 venus ... allocating the names "John's abacus" and "venus" to the according network addresses. John's abacus and venus will replace the cryptic address names on the monitor. - Served interface - the serial interface served by the modem server or CAPI - Status - status of the modem server. Possible states: - free the modem server is available at the moment - Ser. <Client> the modem server is just serving the client named <Client> - Res. <Client> the modem server is presently reserved for the client <Client>. - locally in use The modem server is presently used locally in the /"C" mode (for example a user in the mailbox) - Sent / received bytes - number of bytes transmitted in the current session. This information will be held until the start of a new session. - Identification - the identification of the modem server (/Na). 7 Programs Using INT 14 (BIOS) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The fossil driver is to be understood as an extension to the BIOS-INT 14 interrupt. However, Stomper expects that the software used initializes the fossil driver (not necessary with BIOS routines). For programs only using BIOS-INT 14, NETFOS has to be loaded with the parameter /I. With pure INT 14 applications, Stomper always switches to RTS/CTS data flow control. Approximately 20 seconds after the end of an "INT-14 program" the modem server becomes available for others again. When using fax software, which communicates via INT 14, it is absolutely necessary to lock Stomper on an appropriate rate. The ideal bps rate depends on the modem used. Standard modems transmit faxes with a rate of up to 14400 bps, or 19200 bps on the phone line. In this case the bps rate has to be locked on 19200 bps. Most modems accept a higher rate, for example 57600 bps, when transmitting faxes. For modems with a maximum baud rate of 9600 bps, Stomper should be locked on 9600 bps (see parameter /L on page 6). 8 Stomper and Windows for Workgroups / Windows 95 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WfW and Windows 95 normally load their own network drivers. This means, in these cases, there are no network protocols available prior to loading Windows. In case you are running Netware or any network with DOS-drivers, you can skip this chapter. Create the file WINSTART.BAT in your Windows-directory, like ----------------------------------- NETFOS /P1 ----------------------------------- The batchfile WINSTART.BAT will be executed by Windows after all system-drivers have been loaded (including network drivers). STCOMM.DRV should be loaded as described in chapter "Complete Installation" Be aware that this version of Stomper only supports 16-bit applications! New 32-bit software uses a different driver. 8.1 Microsoft Network ~~~~~~~~~~~~~~~~~~~~~ Make the following changes to your Windows network setup: Defaultprotocol: NetBEUI NCBS=255 NetHeapSize=20 8.2 Novell Network ~~~~~~~~~~~~~~~~~~ Make the following changes to your Windows network setup: Defaultprotocol: IPX/SPX SPX Connections = 60 9 Installation on a NetWare fileserver (NLM-version) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Copy STMGR.NLM and STOMPER.NLM to the SYS:SYSTEM directory. To install STMGR.NLM on the fileserver, enter load STMGR at the console. To install a modemserver, you will need to install an asynchonous I/O-driver first. This requires the module AIO.NLM and any AIO-driver. The appropriate AIO-driver for standard RS232 is AIOCOMX.NLM. You can download AIO-drivers from Compuserve NOVLIB or from our BBS. Several AIO drivers for Hostess, Digiboard, etc. are available. For available commandline options recognized by STOMPER.NLM and STMGR.NLM, refer to chapter Complete Installation on page 6. Note the different format of STOMPER-option /P for port selection: /P<hardwaretype>,<boardnumber>,<portnumber> The three values are shown when you load the AIO-driver. If you are not sure what to type, you can load STOMPER.NLM without the /P-option. Stomper will let you select the desired port and then display the appropriate commandline you should use in future. If you posess a multi-modemserver version of Stomper, you can load STOMPER.NLM multiple times. If you type unload stomper at the system console, you will disable all running modemservers. Caution!! - There is a bug in the Netware 3.x / 4.x - SPX-protocol. This bug known to STOMPER.NLM and Stomper tries hard to avoid problems that might arise. But wo do strongly advise you to install the following Novell-patches: PATCHMAN.NLM SPXDDFIX.NLM SPXFIX2.NLM These three modules are contained in the archive STRTL3.EXE, that can be downloaded free from Compuserve NOVLIB or from our support BBS. - If you have problems loading AIO.NLM, STOMPER.NLM and STMGR.NLM, and you get a message like "Public symbol IsColorMonitor not found", then you have an old version of CLIB.NLM (Netware 3.11). Just install an updated version, that is part of the archive LIBUP4.EXE (Compuserve NOVLIB or our support BBS) - When loading AIOCOMX, do not use the option "node=..." if possible - You should use AIOCOMX >= 2.11. It should be loaded with the maxrate-option: load aiocomx [...] maxrate=115200 - The use of a FIFO (16550)-serial UART is strongly recommended. 10 Applying access rights ~~~~~~~~~~~~~~~~~~~~~~~~~~ STMGR.NLM provides a mechanism to refuse access to all or specific modemservers by username, stationaddress and/or network. This mechanism is activated, as soon as STMGR.NLM finds a file named QMREST.LST in the same directory, STMGR.NLM is contained in. If this file is not present, no restrictions apply. This file could look like this: [stations] 928485 80A23E42 12Q [nets] 1000002 1000003 1 [names] supervisor Peter 24 Rules: - there are 3 possible sections: [stations], [nets] and [names] - you can omit particular sections. There will be no restrictions for these sections. - if a section is present, it defines objects (stationaddresses, usernames or networkaddresses), that have access to modemservers. All objects of this sectiontype, that are not defined, will not have access to any modemserver. - if only the object is entered in a line, it receives access rights to all modemservers throughout the network. If you additionally enter a list of modemserver-ids - separated by spaces or tabs from the objects designation - the object will only have access to the specified modemservers. - access rights are combined by logical and, which means, the user must qualify by station, network and username (in case restrictions apply respectively) Typically the file QMREST.LST will only contain a [names] or [nets] section. Appendix A Suitable Programs ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ All windows programs, using the functions (API) (provided by windows COMM.DRV) for the interface addressing, are supported. DOS: Not every terminal program supports a fossil driver. An example for a program with FOSSIL support is Telemate (In Options / Terminal, FOSSIL can be selected) For the use of Telemate note the following: in order to work with the dial list, for each listing the fossil driver has to be selected individually. To select the fossil support in Telemate, first the baud rate has to be set to a maximum of 38400bps. Otherwise fossil will be ignored! A short list of programs which have been tested with Stomper: Name Operating Comments system ------------------------------------------------------------------ Telemate DOS extensive and comfortable FX-Term DOS Very easy to handle GUI, works with RoboBoard. Terminate DOS extensive (similar to Telemate). IEMSI support Dos/CIS DOS Compuserve information manager Terminal Windows Terminal program included in windows packet GoCIS Windows Offline Compuserve navigator NavCIS Windows Offline Compuserve navigator WinCIS Windows Compuserve information manager PowerCom Windows terminal program Telix for Windows extensive and comfortable terminal program Windows Transend DOS/Windows terminal / fax RemoteAccess DOS BBS software Frontdoor DOS Fido mailer Binkley DOS Fido mailer Crosspoint DOS Fido / Z net / UUCP - point system Winfax Windows fax software Bitfax Windows fax software Unicom Windows comfortable terminal program Most of these programs are available are available as shareware on our Support BBS (see end of Document). Appendix B NETINFO.EXE ~~~~~~~~~~~~~~~~~~~~~~~~~ This a small diagnostic tool added to the packet, giving some information of the network environment (received from netbios), for example Permanent name: 0000C0039A79 ; network address Jumper: 40 POST result: 00 Version: 0.1 Minutes up: 0 Number of CRC errors: 0 Number of alignment errors: 0 Number of collisions: 0 Number of aborts: 1 Number of transmitted packets: 6 Number of received packets: 10 Number of retransmits: 4 Number of out-of-buffer-counts: 0 Free NCBs: 10 Max. NCBs: 12 Active sessions: 32 Max. packet size: 1024 Names: 1 NFOSMPX1 0 Attention! This tool can only be useful when Netbios is actually installed. Otherwise no useful information will be displayed here! This information is of no use for IPX. Appendix C Tips ~~~~~~~~~~~~~~~~~~ 1. Telemate ~~~~~~~~~~~~ Before you select FOSSIL, be careful to set the speed to not more than 38400 bps. Otherwise Telemate will reject the FOSSIL-Setting (without displaying a message). In case even this fails, the safest way is to edit TM.CFG manually. Just change Connection=Modem to Connection=Fossil and make sure that the entry Port= is correct. Also, FOSSIL has to be selected for every entry in the Dial-List. 2. Terminate ~~~~~~~~~~~~~ The first time Terminate is set up for FOSSIL, it expects that a FOSSIL driver is installed on COM1. This, of course, is not always given (e.g. NETFOS installed on COM2). The FOSSIL-support of Terminate is a little buggy here, and this may result in a system-crash. Workaround: either use NETFOS on COM1 or the first time, you switch Terminate to FOSSIL, do it with a regular FOSSIL driver (like BNU or X00) installed. From then on you can use NETFOS. If you don't have a FOSSIL driver handy, load NETFOS /P1() /P2() This installs NETFOS on both COM1 and COM2. 3. Telix For Windows ~~~~~~~~~~~~~~~~~~~~~ Use the COM-Setting, not FOSSIL! In Windows it is always recommended to use STCOMM whenever possible. Apart from that, the FOSSIL support of early versions of TfW is buggy. 4. pcAnywhere ~~~~~~~~~~~~~~ Use the plain INT14-Setting and do not set higher speeds than 9600 bps. Otherwise pcAnywhere will not be able to initialize the port. To achieve higher speeds, refer to the modemserver switch /L. Appendix D Troubleshooting ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Problem possible source solution / remarks The terminalprogram The terminalprogram might If provided by the terminal doesn't react - no address the hardware software, switch to Fossil characters are directly or INT 14. transmitted In case the software doesn't support a software inter- face, there is no way of redirecting port usage. The terminalprogram is set Call NETFOS /I when using to INT-14, but Netfos BIOS-INT14-routines. wasn't loaded with the /I- option. the wrong port is being set the com-port settings of addressed. the terminal software to the value specified in the commandline of Netfos. Characters are lost A non-buffered serial Use a buffered serial device during transmission hardware is used (UART 16550). Such can be obtained for a small fee in most computer stores. Stomper relies on buffered communications devices more than other COM- software, since it has to deal with many interrupt types at once (timer, network and serial). no handshaking active Usually you have to specify the type of handshaking you want to use in the setup of your communications software. In most cases it's best to set hardware handshaking (RTS/CTS) to on and software handshaking (XON/XOFF) to off. Stomper hangs in Stomper was loaded in Stomper cannot be loaded in cooperative mode high memory high memory when driven in cooperative mode. It works with DOS STCOMM.DRV wasn't Make sure, the line but not with Windows installed or wasn't comm.drv=stcomm.drv is installed correctly placed in the [boot]-section of you SYSTEM.INI-file and that there is only one occurence of a line beginning with "comm.drv=" Fax-sending causes You are using a DOS-Fax- In this case, Stomper sets problems software that uses the the handshake-method to Bios-INT 14 interface. "Hardware". Fax transmission with class 2 expects software flow control. make sure that your modem is set to hardware flowcontrol explicitly XON/XOFF handshaking start Stomper with the doesn't function properly commandline option /R Appendix E What is a FOSSIL driver? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There are various possibilities for a DOS program to address serial interfaces of a PC: There is the hardware related method, communicating directly with the interface components. This method is used very often because it's quick and uncomplicated for the program user - no unnecessary thoughts about a fossil driver and its implementation. "Polite" programs use the 4 functions provided by the computer BIOS (INT 14): Baud rate setting, character transmission, character receive and fetching the interface status. This method has the advantage of being hardware independent (only BIOS has to have the information how to communicate with the hardware - the programmer isn't troubled with that). Big and decisive disadvantage: under DOS, BIOS allows max. 9600 bps, which is out of date today. Furthermore BIOS routines are generally quite slow. Another possibility is the fossil driver, combining the advantages of the solutions mentioned above - speed and hardware independence - troubling the user with only one installation. The fossil driver offers buffered interface communication as an additional function to the BIOS, emulating the interface functions of BIOS. Data arriving at the interface needn't be handled immediately by the software, but are stored in a ring buffer. A program using BIOS for example, has to handle every single character before the next arrives in order to avoid a loss of data. With a fossil driver the data can be fetched and handled in blocks. Appendix F What is a network fossil driver? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It's easy to exploit the advantage of a hardware independent program with the use of a fossil driver. A suitable driver can pretend any digital communication element against such a hardware independent program, for example as COM2. The programm doesn't care how this works, as long as the driver handles the mass of data. Stomper uses this circumstance. A modem server is installed on a network integrated computer linked to a modem. The modem server waits for a network fossil driver connection, which again bluffs to be communicating with a serial interface. At the same time a lot of instruction data and other data are passed over the network, but don't worry, a normal network is hardly concerned with that. Appendix G - How to order ~~~~~~~~~~~~~~~~~~~~~~~~~ We have registration sites in many countries. Run the program ORDER.EXE to get information on pricing and registration sites. You will be prompted to select your country. Appendix H Support ~~~~~~~~~~~~~~~~~~~~~ Pflug Datentechnik can be contacted via Fax 49 / 7156 - 939005 e-mail 100340.1047@compuserve.com Compuserve Pflug 100340,1047 Fido 2:246/1009 (per Crashmail only, please!) Mailbox (see below) Inquiries on the phone are not possible without prior consultation. Current Stomper versions and several shareware/PD software can be downloaded from our mailbox: +49 / 7156 - 939006